<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.1, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- This file documents the use of the GNU compilers.

Copyright © 1988-2023 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "Funding Free Software", the Front-Cover
Texts being (a) (see below), and with the Back-Cover Texts being (b)
(see below).  A copy of the license is included in the section entitled
"GNU Free Documentation License".

(a) The FSF's Front-Cover Text is:

A GNU Manual

(b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU
     software.  Copies published by the Free Software Foundation raise
     funds for GNU development. -->
<title>Hints implementation (Using the GNU Compiler Collection (GCC))</title>

<meta name="description" content="Hints implementation (Using the GNU Compiler Collection (GCC))">
<meta name="keywords" content="Hints implementation (Using the GNU Compiler Collection (GCC))">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta name="viewport" content="width=device-width,initial-scale=1">

<link href="index.html" rel="start" title="Top">
<link href="Indices.html" rel="index" title="Indices">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="C-Implementation.html" rel="up" title="C Implementation">
<link href="Structures-unions-enumerations-and-bit_002dfields-implementation.html" rel="next" title="Structures unions enumerations and bit-fields implementation">
<link href="Arrays-and-pointers-implementation.html" rel="prev" title="Arrays and pointers implementation">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
kbd.key {font-style: normal}
span:hover a.copiable-link {visibility: visible}
ul.mark-bullet {list-style-type: disc}
-->
</style>


</head>

<body lang="en_US">
<div class="section-level-extent" id="Hints-implementation">
<div class="nav-panel">
<p>
Next: <a href="Structures-unions-enumerations-and-bit_002dfields-implementation.html" accesskey="n" rel="next">Structures, Unions, Enumerations, and Bit-Fields</a>, Previous: <a href="Arrays-and-pointers-implementation.html" accesskey="p" rel="prev">Arrays and Pointers</a>, Up: <a href="C-Implementation.html" accesskey="u" rel="up">C Implementation-Defined Behavior</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Indices.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h3 class="section" id="Hints"><span>4.8 Hints<a class="copiable-link" href="#Hints"> &para;</a></span></h3>

<ul class="itemize mark-bullet">
<li><cite class="cite">The extent to which suggestions made by using the <code class="code">register</code>
storage-class specifier are effective (C90 6.5.1, C99 and C11 6.7.1).</cite>

<p>The <code class="code">register</code> specifier affects code generation only in these ways:
</p>
<ul class="itemize mark-bullet">
<li>When used as part of the register variable extension, see
<a class="ref" href="Explicit-Register-Variables.html">Variables in Specified Registers</a>.

</li><li>When <samp class="option">-O0</samp> is in use, the compiler allocates distinct stack
memory for all variables that do not have the <code class="code">register</code>
storage-class specifier; if <code class="code">register</code> is specified, the variable
may have a shorter lifespan than the code would indicate and may never
be placed in memory.

</li><li>On some rare x86 targets, <code class="code">setjmp</code> doesn&rsquo;t save the registers in
all circumstances.  In those cases, GCC doesn&rsquo;t allocate any variables
in registers unless they are marked <code class="code">register</code>.

</li></ul>

</li><li><cite class="cite">The extent to which suggestions made by using the inline function
specifier are effective (C99 and C11 6.7.4).</cite>

<p>GCC will not inline any functions if the <samp class="option">-fno-inline</samp> option is
used or if <samp class="option">-O0</samp> is used.  Otherwise, GCC may still be unable to
inline a function for many reasons; the <samp class="option">-Winline</samp> option may be
used to determine if a function has not been inlined and why not.
</p>
</li></ul>

</div>



</body>
</html>
